Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 054c0786cdbe64bbfb2acddf503be97151824bc85798edbebc1944acad46a72c

Tx prefix hash: e77736f56d48a62b26699968e3fa6169223baf7b150e06c0dc0490037b120832
Tx public key: d3fd8d0eb2162c1fbb2323359956eb561fce7ee4bc1077117d9cd2ddacb945c6
Timestamp: 1702434703 Timestamp [UCT]: 2023-12-13 02:31:43 Age [y:d:h:m:s]: 01:336:17:32:34
Block: 911941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499509 RingCT/type: yes/0
Extra: 01d3fd8d0eb2162c1fbb2323359956eb561fce7ee4bc1077117d9cd2ddacb945c602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a55188f6e5cd0f255a0d9f0c1253d0c793bf8c5d57a7b59784e50270e8e4f0d3 0.600000000000 1369159 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": 911951, "vin": [ { "gen": { "height": 911941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a55188f6e5cd0f255a0d9f0c1253d0c793bf8c5d57a7b59784e50270e8e4f0d3" } } ], "extra": [ 1, 211, 253, 141, 14, 178, 22, 44, 31, 187, 35, 35, 53, 153, 86, 235, 86, 31, 206, 126, 228, 188, 16, 119, 17, 125, 156, 210, 221, 172, 185, 69, 198, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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