Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45b2f2ece97c2cd1488ab9ce806a9f4a9e86f4646c0e0d8a18fb4c5f50ae446

Tx prefix hash: 68def3f1e81410443d990f34fd22f8d363f78d012473ec057baf676dc071db51
Tx public key: 4f71372b7b054e1bf3a24002f95fbe35bd316e19937b20d2a1dbd0d62f838c32
Timestamp: 1725112354 Timestamp [UCT]: 2024-08-31 13:52:34 Age [y:d:h:m:s]: 00:221:04:08:09
Block: 1099934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157928 RingCT/type: yes/0
Extra: 014f71372b7b054e1bf3a24002f95fbe35bd316e19937b20d2a1dbd0d62f838c3202110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc80ac8c4c475f8f6b0f15ad18bf42aaeb441b51487de3d42f414a2cedbad3ba 0.600000000000 1575903 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": 1099944, "vin": [ { "gen": { "height": 1099934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc80ac8c4c475f8f6b0f15ad18bf42aaeb441b51487de3d42f414a2cedbad3ba" } } ], "extra": [ 1, 79, 113, 55, 43, 123, 5, 78, 27, 243, 162, 64, 2, 249, 95, 190, 53, 189, 49, 110, 25, 147, 123, 32, 210, 161, 219, 208, 214, 47, 131, 140, 50, 2, 17, 0, 0, 0, 10, 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