Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9abe47576d533726990b272b34a92a38fbe442785ef8f0dd7864605ee8dd341c

Tx prefix hash: 206f4b9922bdd24bce6024a56959e972fc3d8482a4f13da61decef36edc6ef8b
Tx public key: a20b4b3fedc7ccb5cbe3c49b708d353df9cd3886a0f4115940acb5870402b18e
Timestamp: 1733743636 Timestamp [UCT]: 2024-12-09 11:27:16 Age [y:d:h:m:s]: 00:101:16:13:17
Block: 1171393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72475 RingCT/type: yes/0
Extra: 01a20b4b3fedc7ccb5cbe3c49b708d353df9cd3886a0f4115940acb5870402b18e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a1ac07824d331ec5f4bc9cf04fa0014081df6a17b0221ae3f61b4c17a6d1a2 0.600000000000 1657144 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": 1171403, "vin": [ { "gen": { "height": 1171393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a1ac07824d331ec5f4bc9cf04fa0014081df6a17b0221ae3f61b4c17a6d1a2" } } ], "extra": [ 1, 162, 11, 75, 63, 237, 199, 204, 181, 203, 227, 196, 155, 112, 141, 53, 61, 249, 205, 56, 134, 160, 244, 17, 89, 64, 172, 181, 135, 4, 2, 177, 142, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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