Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d827b1d3ec8fd53988a1a7d727e7a52ab6904c5a37ed0d44c84575e97f1c61d

Tx prefix hash: b25ec225786d1beb48b7d3d1827ac009ac8e7247f26078e30e2c45e379883dc3
Tx public key: fef8b4831c0e240e9e89cf7e80b9193a5cf166d5b5889a7caaa1498293388890
Timestamp: 1712702549 Timestamp [UCT]: 2024-04-09 22:42:29 Age [y:d:h:m:s]: 01:009:01:25:39
Block: 997033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267459 RingCT/type: yes/0
Extra: 01fef8b4831c0e240e9e89cf7e80b9193a5cf166d5b5889a7caaa149829338889002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 031e6325b46c06d78d31037ee7122fbe545b1165a436d40549b274f378d9dd97 0.600000000000 1457461 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": 997043, "vin": [ { "gen": { "height": 997033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "031e6325b46c06d78d31037ee7122fbe545b1165a436d40549b274f378d9dd97" } } ], "extra": [ 1, 254, 248, 180, 131, 28, 14, 36, 14, 158, 137, 207, 126, 128, 185, 25, 58, 92, 241, 102, 213, 181, 136, 154, 124, 170, 161, 73, 130, 147, 56, 136, 144, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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