Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0818e8c87304a956a3b046f29c544c5a1a24f27ae439ee5c4725224c1c08a55b

Tx prefix hash: 013b37ec85c90a93a81d7949d483653d1c50a3a1d5b8d9082a6b27d0cc979ebd
Tx public key: 5b889fe89aec2cb471b7271624bd8f9da0bdf21a2376a4c106c4d636f5f6b023
Timestamp: 1699124110 Timestamp [UCT]: 2023-11-04 18:55:10 Age [y:d:h:m:s]: 01:152:02:36:27
Block: 884737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369650 RingCT/type: yes/0
Extra: 015b889fe89aec2cb471b7271624bd8f9da0bdf21a2376a4c106c4d636f5f6b023021100000002faf35c9c000000000000000000

1 output(s) for total of 0.718619591000 dcy

stealth address amount amount idx
00: f6b66fec8541a737a947fdce8241109b24833608fc1bf41cd53d7ae46ae2d2db 0.718619591000 1340484 of 0

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": 884747, "vin": [ { "gen": { "height": 884737 } } ], "vout": [ { "amount": 718619591, "target": { "key": "f6b66fec8541a737a947fdce8241109b24833608fc1bf41cd53d7ae46ae2d2db" } } ], "extra": [ 1, 91, 136, 159, 232, 154, 236, 44, 180, 113, 183, 39, 22, 36, 189, 143, 157, 160, 189, 242, 26, 35, 118, 164, 193, 6, 196, 214, 54, 245, 246, 176, 35, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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