Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce0005a4661d318a132defa4000c9f37e3c3e8af6b5aa6930bcbe0df070c7188

Tx prefix hash: e09ec612a85fbec8b8545d1ab19493a8a0c20211a53b4b7c98590693dfae2b5c
Tx public key: 85e1207f413da1b64c91bf3fcde316f4f2cc6e78682e74f205ce2866e5bdd44a
Timestamp: 1702358254 Timestamp [UCT]: 2023-12-12 05:17:34 Age [y:d:h:m:s]: 01:186:07:12:53
Block: 911296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394233 RingCT/type: yes/0
Extra: 0185e1207f413da1b64c91bf3fcde316f4f2cc6e78682e74f205ce2866e5bdd44a021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd728eab05cb896d505f7524845620e38db9f64158469b5215007d2515216c32 0.600000000000 1368477 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": 911306, "vin": [ { "gen": { "height": 911296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd728eab05cb896d505f7524845620e38db9f64158469b5215007d2515216c32" } } ], "extra": [ 1, 133, 225, 32, 127, 65, 61, 161, 182, 76, 145, 191, 63, 205, 227, 22, 244, 242, 204, 110, 120, 104, 46, 116, 242, 5, 206, 40, 102, 229, 189, 212, 74, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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