Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbf7afc0058aed0311282de15a8e60293ec2a79e9a0b37a77e09297cde8dc28a

Tx prefix hash: b5b2bbf3cf8223b702d444e01665fb9b5bf2c1b011dd46d19d469d3acc3d3303
Tx public key: 3538a98cabeb36ac740d2069e6c4691bdcb64c752d984412954af3b4298908e7
Timestamp: 1724749758 Timestamp [UCT]: 2024-08-27 09:09:18 Age [y:d:h:m:s]: 00:119:03:09:15
Block: 1096924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85231 RingCT/type: yes/0
Extra: 013538a98cabeb36ac740d2069e6c4691bdcb64c752d984412954af3b4298908e702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ac6f20d9cf1e75252a49011b3cf356e2d49a797f8ad58063c8cfac8fd5a13bd 0.600000000000 1572139 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": 1096934, "vin": [ { "gen": { "height": 1096924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ac6f20d9cf1e75252a49011b3cf356e2d49a797f8ad58063c8cfac8fd5a13bd" } } ], "extra": [ 1, 53, 56, 169, 140, 171, 235, 54, 172, 116, 13, 32, 105, 230, 196, 105, 27, 220, 182, 76, 117, 45, 152, 68, 18, 149, 74, 243, 180, 41, 137, 8, 231, 2, 17, 0, 0, 0, 5, 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