Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b559f2294076b97a2c87b9ceffbdaafea81a3c79802f86aa25c3546882025bcb

Tx prefix hash: 74c31f6029b71be65df885fd4a6359fc3aee282dffe42f445913fbba13408e76
Tx public key: f66221dc5947b2eb43aaee2374f77e8ffab9353ee9da2ba68f66e39da8ce6707
Timestamp: 1695626529 Timestamp [UCT]: 2023-09-25 07:22:09 Age [y:d:h:m:s]: 01:264:19:35:19
Block: 855685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450285 RingCT/type: yes/0
Extra: 01f66221dc5947b2eb43aaee2374f77e8ffab9353ee9da2ba68f66e39da8ce670702110000000675e3f0e9000000000000000000

1 output(s) for total of 0.896933885000 dcy

stealth address amount amount idx
00: 12addfbf6202007f1ec08e3ea4ae05c0e701454c4b1e3ce7c35a596f2c0d11c1 0.896933885000 1309721 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": 855695, "vin": [ { "gen": { "height": 855685 } } ], "vout": [ { "amount": 896933885, "target": { "key": "12addfbf6202007f1ec08e3ea4ae05c0e701454c4b1e3ce7c35a596f2c0d11c1" } } ], "extra": [ 1, 246, 98, 33, 220, 89, 71, 178, 235, 67, 170, 238, 35, 116, 247, 126, 143, 250, 185, 53, 62, 233, 218, 43, 166, 143, 102, 227, 157, 168, 206, 103, 7, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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