Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9bdeab811b64852835faf1452c16d4adcaf2c6cabec76401f3a57a36e176aca

Tx prefix hash: 1e7b644c8c2e792e8dcbec568387dd202de82ffb9faedaa4a5dd2861fef122e9
Tx public key: 9e6e2b67930ec63f253f650a7478b2698d48b42fe94e8cdc902d961f83b85122
Timestamp: 1722159240 Timestamp [UCT]: 2024-07-28 09:34:00 Age [y:d:h:m:s]: 01:140:13:31:18
Block: 1075454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359002 RingCT/type: yes/0
Extra: 019e6e2b67930ec63f253f650a7478b2698d48b42fe94e8cdc902d961f83b8512202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f8783a05c904f145b1146e9a45b730889479a92c9ac5aa86b19c362e1e0c4b9 0.600000000000 1547981 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": 1075464, "vin": [ { "gen": { "height": 1075454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f8783a05c904f145b1146e9a45b730889479a92c9ac5aa86b19c362e1e0c4b9" } } ], "extra": [ 1, 158, 110, 43, 103, 147, 14, 198, 63, 37, 63, 101, 10, 116, 120, 178, 105, 141, 72, 180, 47, 233, 78, 140, 220, 144, 45, 150, 31, 131, 184, 81, 34, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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