Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0efec8cd06760c55f7c890908f122d9f5e0054365789f0ab55e03e734ee227b5

Tx prefix hash: ec490832d6c40df9fc6a3e77b7c62e4ef1fd12901d262575790255e0ba8a7941
Tx public key: ddc59e4bf2da4a4cb390541d4f1b27309bf36934168ac50767169a44ea55c2b9
Timestamp: 1723151974 Timestamp [UCT]: 2024-08-08 21:19:34 Age [y:d:h:m:s]: 00:220:14:54:35
Block: 1083684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157580 RingCT/type: yes/0
Extra: 01ddc59e4bf2da4a4cb390541d4f1b27309bf36934168ac50767169a44ea55c2b902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d65add6c495a905830aee947de3f296d0161843b548099f477c04fade0c8e83e 0.600000000000 1557691 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": 1083694, "vin": [ { "gen": { "height": 1083684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d65add6c495a905830aee947de3f296d0161843b548099f477c04fade0c8e83e" } } ], "extra": [ 1, 221, 197, 158, 75, 242, 218, 74, 76, 179, 144, 84, 29, 79, 27, 39, 48, 155, 243, 105, 52, 22, 138, 197, 7, 103, 22, 154, 68, 234, 85, 194, 185, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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