Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333b695387ab3b5f435281766740b2baf442e06f1d208bcb8b02c9207bbedd3c

Tx prefix hash: 508af27bcfa96420cd36dc8b4a45bf3f03a39fae1765ad5f472b27066296b643
Tx public key: 478e18ec8784106f49f05729d3d9b8dce09b7e4c54e1c39cb8875eaaeb32a0dc
Timestamp: 1694129271 Timestamp [UCT]: 2023-09-07 23:27:51 Age [y:d:h:m:s]: 01:265:14:07:06
Block: 843254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450974 RingCT/type: yes/0
Extra: 01478e18ec8784106f49f05729d3d9b8dce09b7e4c54e1c39cb8875eaaeb32a0dc02110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.986164837000 dcy

stealth address amount amount idx
00: cc2c7cea218c47ef7cbcf6373fd35d804df6f5a07d429d2888e5354423fd622f 0.986164837000 1296470 of 0

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": 843264, "vin": [ { "gen": { "height": 843254 } } ], "vout": [ { "amount": 986164837, "target": { "key": "cc2c7cea218c47ef7cbcf6373fd35d804df6f5a07d429d2888e5354423fd622f" } } ], "extra": [ 1, 71, 142, 24, 236, 135, 132, 16, 111, 73, 240, 87, 41, 211, 217, 184, 220, 224, 155, 126, 76, 84, 225, 195, 156, 184, 135, 94, 170, 235, 50, 160, 220, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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