Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202231d66e8ef4a2a3b47b190f5da8ae9df6c5eb53b5bd8806e17a7ff80eb688

Tx prefix hash: 837f9b2ba1af38a3bf70714f1b4795701497bd8564108a7e1793d9af15a6baad
Tx public key: 55ba8f77b24c52aa93d978e1b53a12bc60476660b4ef2f2a526b3d064489d7d2
Timestamp: 1734594543 Timestamp [UCT]: 2024-12-19 07:49:03 Age [y:d:h:m:s]: 00:101:16:42:52
Block: 1178460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72444 RingCT/type: yes/0
Extra: 0155ba8f77b24c52aa93d978e1b53a12bc60476660b4ef2f2a526b3d064489d7d2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42008a6c77dfe40185158520bafd71f40ccff21e01a5782130c730e243d15f3b 0.600000000000 1664847 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": 1178470, "vin": [ { "gen": { "height": 1178460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42008a6c77dfe40185158520bafd71f40ccff21e01a5782130c730e243d15f3b" } } ], "extra": [ 1, 85, 186, 143, 119, 178, 76, 82, 170, 147, 217, 120, 225, 181, 58, 18, 188, 96, 71, 102, 96, 180, 239, 47, 42, 82, 107, 61, 6, 68, 137, 215, 210, 2, 17, 0, 0, 0, 1, 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