Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337a11bee11d4c0c9195983053ed804118ec2b7c3a01c015fd042326a9c737fc

Tx prefix hash: c73aaa8a406160c16d62909f961c0499ea68d5bd2ee7f9a97e85fe14ff5c92fe
Tx public key: 8359c251ffcdb6e4860111f6cb3ce0313942c6a23b9536989567bb8a3d4f1bab
Timestamp: 1737986784 Timestamp [UCT]: 2025-01-27 14:06:24 Age [y:d:h:m:s]: 00:141:11:13:34
Block: 1206281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101045 RingCT/type: yes/0
Extra: 018359c251ffcdb6e4860111f6cb3ce0313942c6a23b9536989567bb8a3d4f1bab021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b19709ebe17795cc481d2398893f6aa4037b3f39bede23a7d05a190e4b2a1c1 0.600000000000 1692984 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": 1206291, "vin": [ { "gen": { "height": 1206281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b19709ebe17795cc481d2398893f6aa4037b3f39bede23a7d05a190e4b2a1c1" } } ], "extra": [ 1, 131, 89, 194, 81, 255, 205, 182, 228, 134, 1, 17, 246, 203, 60, 224, 49, 57, 66, 198, 162, 59, 149, 54, 152, 149, 103, 187, 138, 61, 79, 27, 171, 2, 17, 0, 0, 0, 7, 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