Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d6270d4b18403566d0b1dfc24ac783a422ee1043e300942dc0e7c6d54f01a6

Tx prefix hash: 977c63b52dcb4799d1c67ff93e48e423ee813541a22cfedb344d32a5ca15799c
Tx public key: d66b1db9d44eacd7413ced881fe2d844ed8fa403166ff6ee89ff1c435a05cc2d
Timestamp: 1725422804 Timestamp [UCT]: 2024-09-04 04:06:44 Age [y:d:h:m:s]: 00:237:10:56:06
Block: 1102513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169583 RingCT/type: yes/0
Extra: 01d66b1db9d44eacd7413ced881fe2d844ed8fa403166ff6ee89ff1c435a05cc2d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c9a626ef734947ad0008fa0a3a4c00426566126519f99a96d8f4aba5aef79f 0.600000000000 1578980 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": 1102523, "vin": [ { "gen": { "height": 1102513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c9a626ef734947ad0008fa0a3a4c00426566126519f99a96d8f4aba5aef79f" } } ], "extra": [ 1, 214, 107, 29, 185, 212, 78, 172, 215, 65, 60, 237, 136, 31, 226, 216, 68, 237, 143, 164, 3, 22, 111, 246, 238, 137, 255, 28, 67, 90, 5, 204, 45, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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