Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438533423fcbf642136d8e4d9330178d87af5edfe3d516c4ce0a056aaf26e9dc

Tx prefix hash: 5c34eedbf3a2da254e51f6a8036350ceb96e5784ce3b210b9fdcda9947c2ad2c
Tx public key: 236eee5b1f974e32f50df193df244dd64f9df3362c686ffe0817fa0dd5294091
Timestamp: 1737389249 Timestamp [UCT]: 2025-01-20 16:07:29 Age [y:d:h:m:s]: 00:148:10:16:40
Block: 1201520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105835 RingCT/type: yes/0
Extra: 01236eee5b1f974e32f50df193df244dd64f9df3362c686ffe0817fa0dd5294091021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a66d3218c1830a26f4e9fdbbf521c4273db21f6869563f87b7b9f63395bc46d5 0.600000000000 1688173 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": 1201530, "vin": [ { "gen": { "height": 1201520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a66d3218c1830a26f4e9fdbbf521c4273db21f6869563f87b7b9f63395bc46d5" } } ], "extra": [ 1, 35, 110, 238, 91, 31, 151, 78, 50, 245, 13, 241, 147, 223, 36, 77, 214, 79, 157, 243, 54, 44, 104, 111, 254, 8, 23, 250, 13, 213, 41, 64, 145, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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