Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbcd660adecc6160619d4f491257abd51a8a762d1a149f6b015da75dd44dd80e

Tx prefix hash: 8d4a4e6333fd1a78004bf4d94e6089057f91620cffb40ae0000d41361e95fb9e
Tx public key: 0bcd518ec7dbc68079554d84b1e8ebf9a652bbc5add986000bbd7d06b4c5793b
Timestamp: 1721554562 Timestamp [UCT]: 2024-07-21 09:36:02 Age [y:d:h:m:s]: 00:188:22:01:27
Block: 1070432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135132 RingCT/type: yes/0
Extra: 010bcd518ec7dbc68079554d84b1e8ebf9a652bbc5add986000bbd7d06b4c5793b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb2d916df1206fde63fdff8f0c1782b0321fcc2bbb07f03dc0502bd4cf367b3 0.600000000000 1542265 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": 1070442, "vin": [ { "gen": { "height": 1070432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb2d916df1206fde63fdff8f0c1782b0321fcc2bbb07f03dc0502bd4cf367b3" } } ], "extra": [ 1, 11, 205, 81, 142, 199, 219, 198, 128, 121, 85, 77, 132, 177, 232, 235, 249, 166, 82, 187, 197, 173, 217, 134, 0, 11, 189, 125, 6, 180, 197, 121, 59, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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