Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda53683370a78902e8d6b92ecb0379e7977511114c2b78e2b94d1101334758b

Tx prefix hash: 95107d7ccd6b51e50e731bb612c487680e5e89e328fec90aff13222029882159
Tx public key: 0d621df8a0a1b5cb67fd7f9512c68e4cdcfc5af593fc4703bf762aa3af1ce764
Timestamp: 1648123286 Timestamp [UCT]: 2022-03-24 12:01:26 Age [y:d:h:m:s]: 02:356:03:15:46
Block: 465379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773824 RingCT/type: yes/0
Extra: 010d621df8a0a1b5cb67fd7f9512c68e4cdcfc5af593fc4703bf762aa3af1ce7640211000000015eb576c5000000000000000000

1 output(s) for total of 17.620021793000 dcy

stealth address amount amount idx
00: e4d3a2017a66ccb13fbc10c5deb1fa8e3bab606699ba597d5e3cee0ba4327022 17.620021793000 883472 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": 465389, "vin": [ { "gen": { "height": 465379 } } ], "vout": [ { "amount": 17620021793, "target": { "key": "e4d3a2017a66ccb13fbc10c5deb1fa8e3bab606699ba597d5e3cee0ba4327022" } } ], "extra": [ 1, 13, 98, 29, 248, 160, 161, 181, 203, 103, 253, 127, 149, 18, 198, 142, 76, 220, 252, 90, 245, 147, 252, 71, 3, 191, 118, 42, 163, 175, 28, 231, 100, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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