Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372652279970264faf54539debd4dba9587f8c69f2c995e07a0368d5f48cb481

Tx prefix hash: 4ab1a6012c679e6ccf70d7f5d851fd47c1f80796703145decc607d423b5751b8
Tx public key: 1c78d615d390929475ebee411abd8a75eb6c334cf0e283a51f04a22bac7998e6
Timestamp: 1723650765 Timestamp [UCT]: 2024-08-14 15:52:45 Age [y:d:h:m:s]: 01:086:17:40:43
Block: 1087825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320449 RingCT/type: yes/0
Extra: 011c78d615d390929475ebee411abd8a75eb6c334cf0e283a51f04a22bac7998e6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25448b94028229e729fd3fb7e07596d71dfe5da954dd126b2a9c2a6c4d3d6c6e 0.600000000000 1562436 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": 1087835, "vin": [ { "gen": { "height": 1087825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25448b94028229e729fd3fb7e07596d71dfe5da954dd126b2a9c2a6c4d3d6c6e" } } ], "extra": [ 1, 28, 120, 214, 21, 211, 144, 146, 148, 117, 235, 238, 65, 26, 189, 138, 117, 235, 108, 51, 76, 240, 226, 131, 165, 31, 4, 162, 43, 172, 121, 152, 230, 2, 17, 0, 0, 0, 2, 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