Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf849d65447d0b0e946b70559a96d226deb1dc168e1f984e0f5b9df25ab8426f

Tx prefix hash: 862c99df2eaa5179825203dc4d3c65f55c1aefed52b23ed0c2d234e0f96a020f
Tx public key: 7648ef48232cf7800c9553ee0a364dafcacfa1321bda3539abf2f09762df8ae7
Timestamp: 1718536853 Timestamp [UCT]: 2024-06-16 11:20:53 Age [y:d:h:m:s]: 00:332:11:19:42
Block: 1045436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237613 RingCT/type: yes/0
Extra: 017648ef48232cf7800c9553ee0a364dafcacfa1321bda3539abf2f09762df8ae702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe54f4721811dca40ff43335b797b6905c38d5ebfa3ac6b4fd20224e4f6d9771 0.600000000000 1515007 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": 1045446, "vin": [ { "gen": { "height": 1045436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe54f4721811dca40ff43335b797b6905c38d5ebfa3ac6b4fd20224e4f6d9771" } } ], "extra": [ 1, 118, 72, 239, 72, 35, 44, 247, 128, 12, 149, 83, 238, 10, 54, 77, 175, 202, 207, 161, 50, 27, 218, 53, 57, 171, 242, 240, 151, 98, 223, 138, 231, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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