Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b2f26b1920ce2d8d66c19a156eb8d1e592a9fffc56914b3f2901e5517f73a9

Tx prefix hash: f446a458cd27d520b43c1ab6789e4f47ebc3d6d4098c2859f09c30f6ea50202f
Tx public key: 0c13e06f81dd0f37cac64e08c09bfed4ff242c34c6b3658550505bf10691a493
Timestamp: 1731182106 Timestamp [UCT]: 2024-11-09 19:55:06 Age [y:d:h:m:s]: 00:014:10:50:52
Block: 1150178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10335 RingCT/type: yes/0
Extra: 010c13e06f81dd0f37cac64e08c09bfed4ff242c34c6b3658550505bf10691a493021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f06fa01ceb9d6e4e67d3c7098cc94df8feb3ccc02740ae6f20dc9cde7fa572 0.600000000000 1635409 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": 1150188, "vin": [ { "gen": { "height": 1150178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f06fa01ceb9d6e4e67d3c7098cc94df8feb3ccc02740ae6f20dc9cde7fa572" } } ], "extra": [ 1, 12, 19, 224, 111, 129, 221, 15, 55, 202, 198, 78, 8, 192, 155, 254, 212, 255, 36, 44, 52, 198, 179, 101, 133, 80, 80, 91, 241, 6, 145, 164, 147, 2, 17, 0, 0, 0, 2, 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