Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7d8aea4d198c1ae4cab3be67bf0ad32ae18a37f57ecec53fd5ff5fc8d9720d7

Tx prefix hash: 51ff8df79e3a5aaedb7204b4175b2ce136b45248892c27240dc1bd842b7e5847
Tx public key: 65a0eb409a946bdb3a798c01fbbb2e3f4f3c4507594edf6ab1210a46754882f6
Timestamp: 1729752962 Timestamp [UCT]: 2024-10-24 06:56:02 Age [y:d:h:m:s]: 00:236:07:25:45
Block: 1138384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168624 RingCT/type: yes/0
Extra: 0165a0eb409a946bdb3a798c01fbbb2e3f4f3c4507594edf6ab1210a46754882f6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0c57e05fdc80bb85a1399641fbaeef7e28a3be6e6d799bc0b632f3774e46c44 0.600000000000 1622037 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": 1138394, "vin": [ { "gen": { "height": 1138384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0c57e05fdc80bb85a1399641fbaeef7e28a3be6e6d799bc0b632f3774e46c44" } } ], "extra": [ 1, 101, 160, 235, 64, 154, 148, 107, 219, 58, 121, 140, 1, 251, 187, 46, 63, 79, 60, 69, 7, 89, 78, 223, 106, 177, 33, 10, 70, 117, 72, 130, 246, 2, 17, 0, 0, 0, 3, 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