Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a12753c499838ed35c210321012bd452471ca275c510ee3c8eef5f5fee77720

Tx prefix hash: f99f539b403887c107abcd5d9dbe7ca5369961d906294b2ede8683b63aeaec0e
Tx public key: 6ecbe8a8cf5c2e1c8638d336ac2c7a4686331341450285286d4407a1e82d5b8c
Timestamp: 1737380095 Timestamp [UCT]: 2025-01-20 13:34:55 Age [y:d:h:m:s]: 00:053:02:16:04
Block: 1201443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37785 RingCT/type: yes/0
Extra: 016ecbe8a8cf5c2e1c8638d336ac2c7a4686331341450285286d4407a1e82d5b8c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d94961a4fb26eb0a7188907aa1403b704c1c97a7e2276d516ac0be1a63062a3 0.600000000000 1688096 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": 1201453, "vin": [ { "gen": { "height": 1201443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d94961a4fb26eb0a7188907aa1403b704c1c97a7e2276d516ac0be1a63062a3" } } ], "extra": [ 1, 110, 203, 232, 168, 207, 92, 46, 28, 134, 56, 211, 54, 172, 44, 122, 70, 134, 51, 19, 65, 69, 2, 133, 40, 109, 68, 7, 161, 232, 45, 91, 140, 2, 17, 0, 0, 0, 3, 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