Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f51ffb8e13ef10df359a4b0eeaac8ad5c662727d5fa4485f78b4a0fa99c656

Tx prefix hash: bfa032a8cf5ef1a41e15379ee52e0c285b56d1021b9cbdcd7e8e5d13ba142ddb
Tx public key: 552df3ebe930f73abf08dfdf847c1fbba640777b1da4dd76c968234e1016d6bc
Timestamp: 1703564094 Timestamp [UCT]: 2023-12-26 04:14:54 Age [y:d:h:m:s]: 01:087:15:47:14
Block: 921293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323765 RingCT/type: yes/0
Extra: 01552df3ebe930f73abf08dfdf847c1fbba640777b1da4dd76c968234e1016d6bc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b32deed68bcb2f8d5d49685a011ad879f58a54c1392838ed5a85e4fec29a79c 0.600000000000 1378979 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": 921303, "vin": [ { "gen": { "height": 921293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b32deed68bcb2f8d5d49685a011ad879f58a54c1392838ed5a85e4fec29a79c" } } ], "extra": [ 1, 85, 45, 243, 235, 233, 48, 247, 58, 191, 8, 223, 223, 132, 124, 31, 187, 166, 64, 119, 123, 29, 164, 221, 118, 201, 104, 35, 78, 16, 22, 214, 188, 2, 17, 0, 0, 0, 2, 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