Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45653891ab5483848f651d4365b89e82cdc2d4ae372ee2121e29f0eecb99338b

Tx prefix hash: b0b6d994ea01172f214b46b9281d61fcefc17798b76dcd76b84bfd45cf38376b
Tx public key: c5ddf2bda6bd732e80370f9496c7a202b11aa3dc20d7c0e80b76bb14255d2859
Timestamp: 1722620575 Timestamp [UCT]: 2024-08-02 17:42:55 Age [y:d:h:m:s]: 01:098:11:50:05
Block: 1079277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328880 RingCT/type: yes/0
Extra: 01c5ddf2bda6bd732e80370f9496c7a202b11aa3dc20d7c0e80b76bb14255d2859021100000001ef5a8513000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844867949d26058d9c35c77ce0a2e0a1ae70ea3caad009d1f7c365c3e65c5624 0.600000000000 1552160 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": 1079287, "vin": [ { "gen": { "height": 1079277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844867949d26058d9c35c77ce0a2e0a1ae70ea3caad009d1f7c365c3e65c5624" } } ], "extra": [ 1, 197, 221, 242, 189, 166, 189, 115, 46, 128, 55, 15, 148, 150, 199, 162, 2, 177, 26, 163, 220, 32, 215, 192, 232, 11, 118, 187, 20, 37, 93, 40, 89, 2, 17, 0, 0, 0, 1, 239, 90, 133, 19, 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