Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c957f1bfc27af8467191e8f3295a2f1148dd6b5c102a8976139b41581e683730

Tx prefix hash: 793d6d11e835d03f22a45ce68e7b1cd6dc70e93b1b7f08db566be9c9d72929e6
Tx public key: dbfe1fd18ab99bfdaa24cb5120cad1afff8bca90aed46eb253a2a6852593ef75
Timestamp: 1682811662 Timestamp [UCT]: 2023-04-29 23:41:02 Age [y:d:h:m:s]: 01:256:14:00:21
Block: 749496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444849 RingCT/type: yes/0
Extra: 01dbfe1fd18ab99bfdaa24cb5120cad1afff8bca90aed46eb253a2a6852593ef750211000000027e406890000000000000000000

1 output(s) for total of 2.016549213000 dcy

stealth address amount amount idx
00: d33542eb350ba16397a5d9e1269c74b23500a5c5e4be6d10e50b8c411060a00e 2.016549213000 1197471 of 0

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": 749506, "vin": [ { "gen": { "height": 749496 } } ], "vout": [ { "amount": 2016549213, "target": { "key": "d33542eb350ba16397a5d9e1269c74b23500a5c5e4be6d10e50b8c411060a00e" } } ], "extra": [ 1, 219, 254, 31, 209, 138, 185, 155, 253, 170, 36, 203, 81, 32, 202, 209, 175, 255, 139, 202, 144, 174, 212, 110, 178, 83, 162, 166, 133, 37, 147, 239, 117, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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