Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccf1eb32579c2744506f243533111d958f4ac3500e1956643671509113dca277

Tx prefix hash: 1d4cec2c2be13e4927f1a107248e5b71304ecb719376259ff99cacf445a91e92
Tx public key: 2e5e1e7f1c75e5722beb9a6c711f3e24c6e522f24233832a53f8111e0c5e6597
Timestamp: 1611344528 Timestamp [UCT]: 2021-01-22 19:42:08 Age [y:d:h:m:s]: 03:343:03:05:51
Block: 183540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1003204 RingCT/type: yes/0
Extra: 012e5e1e7f1c75e5722beb9a6c711f3e24c6e522f24233832a53f8111e0c5e65970211000000f4c6b81c9d000000000000000000

1 output(s) for total of 151.306099178000 dcy

stealth address amount amount idx
00: 826435f84bed31a84a0ea85693b8bfad6486ea2dfaeee4eeb5bd7a6b2892c488 151.306099178000 358642 of 0

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": 183550, "vin": [ { "gen": { "height": 183540 } } ], "vout": [ { "amount": 151306099178, "target": { "key": "826435f84bed31a84a0ea85693b8bfad6486ea2dfaeee4eeb5bd7a6b2892c488" } } ], "extra": [ 1, 46, 94, 30, 127, 28, 117, 229, 114, 43, 235, 154, 108, 113, 31, 62, 36, 198, 229, 34, 242, 66, 51, 131, 42, 83, 248, 17, 30, 12, 94, 101, 151, 2, 17, 0, 0, 0, 244, 198, 184, 28, 157, 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