Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7161ad90d5a06068a1377aec8190a2ce521d398c1c8cb292d07e416ce4ca6909

Tx prefix hash: 0d5442b4f487ab33471beb25edc041c1e8af0b516ca542b7f3815bc92f9a77b9
Tx public key: 08e2cdee0d3b9550320d1350ef5e277f1e1159e81ac9167c5dfea8aae4ef4a6c
Timestamp: 1697967481 Timestamp [UCT]: 2023-10-22 09:38:01 Age [y:d:h:m:s]: 01:130:21:33:18
Block: 875102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354539 RingCT/type: yes/0
Extra: 0108e2cdee0d3b9550320d1350ef5e277f1e1159e81ac9167c5dfea8aae4ef4a6c0211000000024b8f5122000000000000000000

1 output(s) for total of 0.773435001000 dcy

stealth address amount amount idx
00: 2eb68ea4167cef83cecc005f11361fbc9a2ce0577611599aeeaad10a424dc92e 0.773435001000 1330346 of 0

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": 875112, "vin": [ { "gen": { "height": 875102 } } ], "vout": [ { "amount": 773435001, "target": { "key": "2eb68ea4167cef83cecc005f11361fbc9a2ce0577611599aeeaad10a424dc92e" } } ], "extra": [ 1, 8, 226, 205, 238, 13, 59, 149, 80, 50, 13, 19, 80, 239, 94, 39, 127, 30, 17, 89, 232, 26, 201, 22, 124, 93, 254, 168, 170, 228, 239, 74, 108, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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