Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a07b7d41752dfdbe7ee3ecb6b2b25e0eb6aca6ea5bd4d198cfede65a061e3fc7

Tx prefix hash: 450ef34d8ddd6a67829a293ddb38e2cb575603c38736939d40f169ad22fc3b4d
Tx public key: 69f80d0949a791dc9c5f43da8e05faa39d91209f0c9e62f2ee614128a8d3c86d
Timestamp: 1737045410 Timestamp [UCT]: 2025-01-16 16:36:50 Age [y:d:h:m:s]: 00:156:02:43:26
Block: 1198721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111237 RingCT/type: yes/0
Extra: 0169f80d0949a791dc9c5f43da8e05faa39d91209f0c9e62f2ee614128a8d3c86d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dee4ba495dca5d0e4102b22a866bfa0c614101a44001112e0c7b9eeffd00491 0.600000000000 1685348 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": 1198731, "vin": [ { "gen": { "height": 1198721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dee4ba495dca5d0e4102b22a866bfa0c614101a44001112e0c7b9eeffd00491" } } ], "extra": [ 1, 105, 248, 13, 9, 73, 167, 145, 220, 156, 95, 67, 218, 142, 5, 250, 163, 157, 145, 32, 159, 12, 158, 98, 242, 238, 97, 65, 40, 168, 211, 200, 109, 2, 17, 0, 0, 0, 1, 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