Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bfcd23b9f90d97edbeba403623187d5a69427f2ebf975fb55464defc98a4d3b9

Tx prefix hash: 34d44d6d23c7c23e440d3862ca28d36c8d5cbf4786caba1fcf912945d96659cd
Tx public key: c829d8e911fd39431d5e8cc252ea854d0f07ea497fe078aae9f471b10692f916
Timestamp: 1727766647 Timestamp [UCT]: 2024-10-01 07:10:47 Age [y:d:h:m:s]: 00:198:22:59:46
Block: 1121950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142002 RingCT/type: yes/0
Extra: 01c829d8e911fd39431d5e8cc252ea854d0f07ea497fe078aae9f471b10692f91602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a4d7f2557365aff91edef40b2457035a93db35753e83af12f4b458d26d56ad 0.600000000000 1604313 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1121960, "vin": [ { "gen": { "height": 1121950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a4d7f2557365aff91edef40b2457035a93db35753e83af12f4b458d26d56ad" } } ], "extra": [ 1, 200, 41, 216, 233, 17, 253, 57, 67, 29, 94, 140, 194, 82, 234, 133, 77, 15, 7, 234, 73, 127, 224, 120, 170, 233, 244, 113, 177, 6, 146, 249, 22, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8