Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe12b27f0e8aa289b22483a9e838a8ae4a8901f699a6f016079ddb6a062d8dd

Tx prefix hash: a7bf5985288be4403ddc40d46953343d9b1c70b18c0afd4496a1d59a73461643
Tx public key: 8f3f3a1a8057d9abe3fa08fdffe0f1d9e8a8414ae72d5109d58c367b6068d2f6
Timestamp: 1729816608 Timestamp [UCT]: 2024-10-25 00:36:48 Age [y:d:h:m:s]: 00:169:22:03:23
Block: 1138905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121241 RingCT/type: yes/0
Extra: 018f3f3a1a8057d9abe3fa08fdffe0f1d9e8a8414ae72d5109d58c367b6068d2f6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f1e594c41142c95d410aef8887f09bda19a1af6756be3710314c9a340a4846c 0.600000000000 1622644 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": 1138915, "vin": [ { "gen": { "height": 1138905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f1e594c41142c95d410aef8887f09bda19a1af6756be3710314c9a340a4846c" } } ], "extra": [ 1, 143, 63, 58, 26, 128, 87, 217, 171, 227, 250, 8, 253, 255, 224, 241, 217, 232, 168, 65, 74, 231, 45, 81, 9, 213, 140, 54, 123, 96, 104, 210, 246, 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