Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc1e467eb339d6c7d9410159dcf5d67e51cc328833caa724d9b732193157805f

Tx prefix hash: c14ef83b210169cbcbb55f4b19559c4cdf38f5c49f536d54f0ea29dd9eca9206
Tx public key: 61a380349d5f9fa3aaac5c6d61401c6f2e99ed040885982e92f75b3e815eace2
Timestamp: 1737098357 Timestamp [UCT]: 2025-01-17 07:19:17 Age [y:d:h:m:s]: 00:155:23:12:55
Block: 1199159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111118 RingCT/type: yes/0
Extra: 0161a380349d5f9fa3aaac5c6d61401c6f2e99ed040885982e92f75b3e815eace202110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428a05d08551f3a63902525adea588b15a6e8d8b309c879d0a16ac1f840cfcbb 0.600000000000 1685788 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": 1199169, "vin": [ { "gen": { "height": 1199159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428a05d08551f3a63902525adea588b15a6e8d8b309c879d0a16ac1f840cfcbb" } } ], "extra": [ 1, 97, 163, 128, 52, 157, 95, 159, 163, 170, 172, 92, 109, 97, 64, 28, 111, 46, 153, 237, 4, 8, 133, 152, 46, 146, 247, 91, 62, 129, 94, 172, 226, 2, 17, 0, 0, 0, 15, 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