Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1ce5a4cc5f7eed17c250134a6a389b8a05fc8dd03e6c7235f90317ae5aa117a

Tx prefix hash: 652f9e02706115cb60fe0cdff4fa8fee8f42da5895f0dad435bdc4f53e0db393
Tx public key: ea2306b361b6d6213e4f344ca0dd8ec3e54bda8d1793e50b5a72cb54c9ec049f
Timestamp: 1732634354 Timestamp [UCT]: 2024-11-26 15:19:14 Age [y:d:h:m:s]: 00:134:21:21:37
Block: 1162201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96221 RingCT/type: yes/0
Extra: 01ea2306b361b6d6213e4f344ca0dd8ec3e54bda8d1793e50b5a72cb54c9ec049f021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b40c232851e5d657a25a1f85bf8ca978a7e561746b2269c4e0b3702e326b7298 0.600000000000 1647856 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": 1162211, "vin": [ { "gen": { "height": 1162201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b40c232851e5d657a25a1f85bf8ca978a7e561746b2269c4e0b3702e326b7298" } } ], "extra": [ 1, 234, 35, 6, 179, 97, 182, 214, 33, 62, 79, 52, 76, 160, 221, 142, 195, 229, 75, 218, 141, 23, 147, 229, 11, 90, 114, 203, 84, 201, 236, 4, 159, 2, 17, 0, 0, 0, 6, 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