Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98c7edc44e19b096943e77789559b22ca98550a60f32b0e68d968b95b46152ee

Tx prefix hash: b1a4161832f8d15c1ae66fe8afa27a1cb535b11d22bb75bd31da9d4235c3d5ec
Tx public key: 5165934eaed007aaed4d16a57b82bcf6fb1cd1e45848e072a3c658690f5d699a
Timestamp: 1734466101 Timestamp [UCT]: 2024-12-17 20:08:21 Age [y:d:h:m:s]: 00:126:10:07:41
Block: 1177397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90125 RingCT/type: yes/0
Extra: 015165934eaed007aaed4d16a57b82bcf6fb1cd1e45848e072a3c658690f5d699a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0458c69e9eac60f234dc48039f30f0ebad289bf0ca61ee2f56e31e2406fd29bf 0.600000000000 1663768 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": 1177407, "vin": [ { "gen": { "height": 1177397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0458c69e9eac60f234dc48039f30f0ebad289bf0ca61ee2f56e31e2406fd29bf" } } ], "extra": [ 1, 81, 101, 147, 78, 174, 208, 7, 170, 237, 77, 22, 165, 123, 130, 188, 246, 251, 28, 209, 228, 88, 72, 224, 114, 163, 198, 88, 105, 15, 93, 105, 154, 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