Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06fabb41861d1647796dc6ae237790c56b31137aa5ec749ee38ad2a6e2d65f3f

Tx prefix hash: ff2b39d8f2e0cd773743a74b272332ed7505b0593223d04b66204ff6c23323dc
Tx public key: f575deaf724d783a45bebf1682cb6545a80091200b3e0ce793d6e9a2a4b3f6e0
Timestamp: 1732300886 Timestamp [UCT]: 2024-11-22 18:41:26 Age [y:d:h:m:s]: 00:001:08:13:54
Block: 1159437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 968 RingCT/type: yes/0
Extra: 01f575deaf724d783a45bebf1682cb6545a80091200b3e0ce793d6e9a2a4b3f6e0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1cf47c74cd04cce765f2cca81d7d7abfacba06894a6904e8611a375e8094fe6 0.600000000000 1645072 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": 1159447, "vin": [ { "gen": { "height": 1159437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1cf47c74cd04cce765f2cca81d7d7abfacba06894a6904e8611a375e8094fe6" } } ], "extra": [ 1, 245, 117, 222, 175, 114, 77, 120, 58, 69, 190, 191, 22, 130, 203, 101, 69, 168, 0, 145, 32, 11, 62, 12, 231, 147, 214, 233, 162, 164, 179, 246, 224, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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