Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b4c3f902193f9bcee9bd6981f943e199c361db32fbe6146a738f6c215d42d9

Tx prefix hash: fa2dea44035a5a1f12fa5b71902f5a77576fb21200f4998f05c0ce9d0ac66e96
Tx public key: d15e5c0505c907cb7cdddc7fb23d922be40c78f538524845461c78b5770eb989
Timestamp: 1722827645 Timestamp [UCT]: 2024-08-05 03:14:05 Age [y:d:h:m:s]: 01:094:23:05:36
Block: 1080994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326351 RingCT/type: yes/0
Extra: 01d15e5c0505c907cb7cdddc7fb23d922be40c78f538524845461c78b5770eb989021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f04a1650cbe3614858b965cb55dd6dc5da7a0e1869072991d3820f588f6374 0.600000000000 1554567 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": 1081004, "vin": [ { "gen": { "height": 1080994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f04a1650cbe3614858b965cb55dd6dc5da7a0e1869072991d3820f588f6374" } } ], "extra": [ 1, 209, 94, 92, 5, 5, 201, 7, 203, 124, 221, 220, 127, 178, 61, 146, 43, 228, 12, 120, 245, 56, 82, 72, 69, 70, 28, 120, 181, 119, 14, 185, 137, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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