Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd812b5369070797a4a9cff00b9bd8c6511771c1c75333fd4d44aceb180b3fa

Tx prefix hash: 473eb07a539435c302ffb9fb6aa99717009059dc2bc22c5082e051699a58ebb5
Tx public key: dff8bfae421eca6c0bacfba36347a3bf3d4c2c75e0ef517bb4551b71ea4f78b3
Timestamp: 1715382971 Timestamp [UCT]: 2024-05-10 23:16:11 Age [y:d:h:m:s]: 00:310:03:40:12
Block: 1019294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221681 RingCT/type: yes/0
Extra: 01dff8bfae421eca6c0bacfba36347a3bf3d4c2c75e0ef517bb4551b71ea4f78b3021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b03a83ec8b79deb40e64b016455adbae92132fd118e9ef58cdaf5dec86a05a1 0.600000000000 1483223 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": 1019304, "vin": [ { "gen": { "height": 1019294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b03a83ec8b79deb40e64b016455adbae92132fd118e9ef58cdaf5dec86a05a1" } } ], "extra": [ 1, 223, 248, 191, 174, 66, 30, 202, 108, 11, 172, 251, 163, 99, 71, 163, 191, 61, 76, 44, 117, 224, 239, 81, 123, 180, 85, 27, 113, 234, 79, 120, 179, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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