Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85d532c3c4edf92c971f5bd32246dac5e2d6f316b7ba87e1c6dfc57e86b26f2

Tx prefix hash: f541acfcf4cf979086e97e7f7cb48f0afe53ff78edc4058406b305a4116c6c1e
Tx public key: fd31ef62e5ec78aa01eef90f6cc19539e56ee16ca167e30f2ee010cd39b6bd12
Timestamp: 1734022132 Timestamp [UCT]: 2024-12-12 16:48:52 Age [y:d:h:m:s]: 00:108:21:16:34
Block: 1173721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77587 RingCT/type: yes/0
Extra: 01fd31ef62e5ec78aa01eef90f6cc19539e56ee16ca167e30f2ee010cd39b6bd12021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14f71bdc4804e7223feb192ac675832a447daa85c8aeea036db8cfd9ff47154c 0.600000000000 1659774 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": 1173731, "vin": [ { "gen": { "height": 1173721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14f71bdc4804e7223feb192ac675832a447daa85c8aeea036db8cfd9ff47154c" } } ], "extra": [ 1, 253, 49, 239, 98, 229, 236, 120, 170, 1, 238, 249, 15, 108, 193, 149, 57, 229, 110, 225, 108, 161, 103, 227, 15, 46, 224, 16, 205, 57, 182, 189, 18, 2, 17, 0, 0, 0, 1, 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