Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954f8e91ac7002e0a455c22a0c5c5ec40290a32b5fa9431bc76243348650572b

Tx prefix hash: 45966e4b81a230bf7062c57b81064e41c07294eb18172112b0beebc6f53dc690
Tx public key: 83738f47ad818d0a82ac8abdc163ad3b7ff5b45c5e2cede1a73002b016941b87
Timestamp: 1702810441 Timestamp [UCT]: 2023-12-17 10:54:01 Age [y:d:h:m:s]: 01:326:08:10:42
Block: 915054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492074 RingCT/type: yes/0
Extra: 0183738f47ad818d0a82ac8abdc163ad3b7ff5b45c5e2cede1a73002b016941b8702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8427f64e94305bfbb0f72b14463f53b2ea5911a4f20d0b6a4c917473cc82df87 0.600000000000 1372432 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": 915064, "vin": [ { "gen": { "height": 915054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8427f64e94305bfbb0f72b14463f53b2ea5911a4f20d0b6a4c917473cc82df87" } } ], "extra": [ 1, 131, 115, 143, 71, 173, 129, 141, 10, 130, 172, 138, 189, 193, 99, 173, 59, 127, 245, 180, 92, 94, 44, 237, 225, 167, 48, 2, 176, 22, 148, 27, 135, 2, 17, 0, 0, 0, 1, 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