Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d194c45713d782f3792219f6d016f6784d9732e9e2b691bdfe05aff2e194970f

Tx prefix hash: 1c399173dede1ece80b7deae21dcecad1a7077f7da087d3d1fdcc2cbeedf309b
Tx public key: 2fb480395bfbbee7221e6e314b53e15394f6fa659fe0fb7c1baab17ec3f8294b
Timestamp: 1730973415 Timestamp [UCT]: 2024-11-07 09:56:55 Age [y:d:h:m:s]: 00:076:08:20:48
Block: 1148443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54584 RingCT/type: yes/0
Extra: 012fb480395bfbbee7221e6e314b53e15394f6fa659fe0fb7c1baab17ec3f8294b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3ee5470e7e728e28b2224177b5da0eb81dfca7683ce35d4f69d4837e39afaf7 0.600000000000 1633286 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": 1148453, "vin": [ { "gen": { "height": 1148443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3ee5470e7e728e28b2224177b5da0eb81dfca7683ce35d4f69d4837e39afaf7" } } ], "extra": [ 1, 47, 180, 128, 57, 91, 251, 190, 231, 34, 30, 110, 49, 75, 83, 225, 83, 148, 246, 250, 101, 159, 224, 251, 124, 27, 170, 177, 126, 195, 248, 41, 75, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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