Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dc8e9a4c151aa2a0849b894d6eb98940ed180c73446cd8b5e6d89d269954a98

Tx prefix hash: 8ab75876207bbb0816e0ed80ccdc00fdf8b54aeeacb2243cda22faae30e085f3
Tx public key: 46bdfe0a045a697b5ba25d9ab72a187af76021b9abd26ff93540f6491024219d
Timestamp: 1754426616 Timestamp [UCT]: 2025-08-05 20:43:36 Age [y:d:h:m:s]: 00:104:09:37:34
Block: 1341003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73619 RingCT/type: yes/0
Extra: 0146bdfe0a045a697b5ba25d9ab72a187af76021b9abd26ff93540f6491024219d021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4fae44ca0ddd4d4bdc5b72833a8f93b27f5fe03745a8c4e54569938c0e71d47 0.600000000000 1828824 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": 1341013, "vin": [ { "gen": { "height": 1341003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4fae44ca0ddd4d4bdc5b72833a8f93b27f5fe03745a8c4e54569938c0e71d47" } } ], "extra": [ 1, 70, 189, 254, 10, 4, 90, 105, 123, 91, 162, 93, 154, 183, 42, 24, 122, 247, 96, 33, 185, 171, 210, 111, 249, 53, 64, 246, 73, 16, 36, 33, 157, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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