Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c72a7087d871335dc6e2fca610ab0e316df9accf10544f429a001ddd86281b

Tx prefix hash: 107f70ab4e1e1e39d7c3953119077b3f0efbd9ebfea712160e3052b86f378780
Tx public key: 6a4cb375c4038831712fedc2711dea0d68e70c47517bfd5b055e2bf88a0d6993
Timestamp: 1703998968 Timestamp [UCT]: 2023-12-31 05:02:48 Age [y:d:h:m:s]: 01:317:06:20:04
Block: 924887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485593 RingCT/type: yes/0
Extra: 016a4cb375c4038831712fedc2711dea0d68e70c47517bfd5b055e2bf88a0d69930211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4263c7dcb8174d302d40c393b6d4c9b029feeb3aa7701322da75eb36613b60b6 0.600000000000 1382647 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": 924897, "vin": [ { "gen": { "height": 924887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4263c7dcb8174d302d40c393b6d4c9b029feeb3aa7701322da75eb36613b60b6" } } ], "extra": [ 1, 106, 76, 179, 117, 196, 3, 136, 49, 113, 47, 237, 194, 113, 29, 234, 13, 104, 231, 12, 71, 81, 123, 253, 91, 5, 94, 43, 248, 138, 13, 105, 147, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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