Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d3c2ebc9009ab7b8e9a13e3a99a59be7df6c37dbc725423732f4e46d36d4d6

Tx prefix hash: d3e422231bcd836a48dcb08961d6a79901c11c9b608901c9b3e7d0d19d748112
Tx public key: f878c6e6c670c18a33f475ff4c85774a8b38dce904efbabe3f84497994f32cd1
Timestamp: 1584447122 Timestamp [UCT]: 2020-03-17 12:12:02 Age [y:d:h:m:s]: 05:042:19:18:35
Block: 84271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186872 RingCT/type: yes/0
Extra: 01f878c6e6c670c18a33f475ff4c85774a8b38dce904efbabe3f84497994f32cd102110000000ad81c26c0000000000000000000

1 output(s) for total of 322.682919893000 dcy

stealth address amount amount idx
00: 7dd1d518736ebec368402b076e6a8cac3b7eb3d8cab168e0bdc02ee5be64c5ca 322.682919893000 152833 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": 84281, "vin": [ { "gen": { "height": 84271 } } ], "vout": [ { "amount": 322682919893, "target": { "key": "7dd1d518736ebec368402b076e6a8cac3b7eb3d8cab168e0bdc02ee5be64c5ca" } } ], "extra": [ 1, 248, 120, 198, 230, 198, 112, 193, 138, 51, 244, 117, 255, 76, 133, 119, 74, 139, 56, 220, 233, 4, 239, 186, 190, 63, 132, 73, 121, 148, 243, 44, 209, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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