Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec42af22cc03f9cffea49c46ef173741385c65d437ef4bf2fdbc1d5b32da0a0d

Tx prefix hash: 8a445795a8a271b413d8622e80e2c5f0709dca3698814c033568dbeccbb5960f
Tx public key: 81051dc86bf2a3d60c8738dbc03e854998762aa034a02a399ea6699c3756f6d7
Timestamp: 1703303737 Timestamp [UCT]: 2023-12-23 03:55:37 Age [y:d:h:m:s]: 01:101:23:25:23
Block: 919130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333997 RingCT/type: yes/0
Extra: 0181051dc86bf2a3d60c8738dbc03e854998762aa034a02a399ea6699c3756f6d70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 762cbeaa05d778e73bbd740fb7b8d53210983f2d9d5669b44f6fdda182f88698 0.600000000000 1376794 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": 919140, "vin": [ { "gen": { "height": 919130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "762cbeaa05d778e73bbd740fb7b8d53210983f2d9d5669b44f6fdda182f88698" } } ], "extra": [ 1, 129, 5, 29, 200, 107, 242, 163, 214, 12, 135, 56, 219, 192, 62, 133, 73, 152, 118, 42, 160, 52, 160, 42, 57, 158, 166, 105, 156, 55, 86, 246, 215, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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