Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a0458b0c8547e4318d0d976fdafc99c16ff0282a28e795985b421c95d49682

Tx prefix hash: 03647784de31b588495d12aa5b15cfa6ed3b267c8e2f26c16d3c94b528026adc
Tx public key: 0f40d423c645f10ee58418b5e3bb7c41537344500dc8bb15c2c846b27732f22b
Timestamp: 1736948198 Timestamp [UCT]: 2025-01-15 13:36:38 Age [y:d:h:m:s]: 00:153:17:44:50
Block: 1197918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109579 RingCT/type: yes/0
Extra: 010f40d423c645f10ee58418b5e3bb7c41537344500dc8bb15c2c846b27732f22b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3436ee0217636f77a62ca4c260a402edfc5214777a74d7e0b0b682797c9e7f 0.600000000000 1684535 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": 1197928, "vin": [ { "gen": { "height": 1197918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3436ee0217636f77a62ca4c260a402edfc5214777a74d7e0b0b682797c9e7f" } } ], "extra": [ 1, 15, 64, 212, 35, 198, 69, 241, 14, 229, 132, 24, 181, 227, 187, 124, 65, 83, 115, 68, 80, 13, 200, 187, 21, 194, 200, 70, 178, 119, 50, 242, 43, 2, 17, 0, 0, 0, 5, 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