Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b94d406bd2e468380cd93c4616031494937d64e24ff3f7a5ad2204f6a35c67b5

Tx prefix hash: d7f176e1d0c7ebb6f688338ef307b0af6374324bf4064db6bd9ae749f40ebee5
Tx public key: f52c9485f3f2d89377072fd6547ce82300d074e312cc6c251f9fd18c2a861c30
Timestamp: 1722676244 Timestamp [UCT]: 2024-08-03 09:10:44 Age [y:d:h:m:s]: 00:203:13:32:44
Block: 1079736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145353 RingCT/type: yes/0
Extra: 01f52c9485f3f2d89377072fd6547ce82300d074e312cc6c251f9fd18c2a861c3002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e92cc8a1e981b0460a78951fcff658bfdd227962cc64f02bd6d947d455b329 0.600000000000 1552825 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": 1079746, "vin": [ { "gen": { "height": 1079736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e92cc8a1e981b0460a78951fcff658bfdd227962cc64f02bd6d947d455b329" } } ], "extra": [ 1, 245, 44, 148, 133, 243, 242, 216, 147, 119, 7, 47, 214, 84, 124, 232, 35, 0, 208, 116, 227, 18, 204, 108, 37, 31, 159, 209, 140, 42, 134, 28, 48, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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