Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7e679c67ecdc329fcda66bc81c279c6f59769696093328cf5cf0daf174ebf05

Tx prefix hash: 000538b4a6122bec7ceaf851398799f01c05b54b3627eaf969b4e42c97eaa2d6
Tx public key: 359279a479e9fb8bb5e9cd49fe4dc094fd9e66fde64b4dab33444a0d9a54ee4a
Timestamp: 1709864451 Timestamp [UCT]: 2024-03-08 02:20:51 Age [y:d:h:m:s]: 01:039:19:59:20
Block: 973531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289468 RingCT/type: yes/0
Extra: 01359279a479e9fb8bb5e9cd49fe4dc094fd9e66fde64b4dab33444a0d9a54ee4a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80073d6bd3b8166ab65ef2f090b0b75865ffdf5fffa59f0ed3f5b95a3d33d4ee 0.600000000000 1433466 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": 973541, "vin": [ { "gen": { "height": 973531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80073d6bd3b8166ab65ef2f090b0b75865ffdf5fffa59f0ed3f5b95a3d33d4ee" } } ], "extra": [ 1, 53, 146, 121, 164, 121, 233, 251, 139, 181, 233, 205, 73, 254, 77, 192, 148, 253, 158, 102, 253, 230, 75, 77, 171, 51, 68, 74, 13, 154, 84, 238, 74, 2, 17, 0, 0, 0, 1, 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