Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a156e4a962eb59ff07590210a160a43067b03ee5b12e064b06937c90f8d06b

Tx prefix hash: 167e94ceadf16fc988be54ee21d8c628a40c900d342f2252fa906f501b243c1c
Tx public key: f00c106da5c23eaf37776b786884f14d1965a9943acf7f8b731efe724f950d2d
Timestamp: 1709951432 Timestamp [UCT]: 2024-03-09 02:30:32 Age [y:d:h:m:s]: 01:070:17:22:51
Block: 974254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311561 RingCT/type: yes/0
Extra: 01f00c106da5c23eaf37776b786884f14d1965a9943acf7f8b731efe724f950d2d02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14a4e30692d3a0dbb0eacd6cd311832fc77a8a28a461d3b5caf787a7d011a4c5 0.600000000000 1434209 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": 974264, "vin": [ { "gen": { "height": 974254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a4e30692d3a0dbb0eacd6cd311832fc77a8a28a461d3b5caf787a7d011a4c5" } } ], "extra": [ 1, 240, 12, 16, 109, 165, 194, 62, 175, 55, 119, 107, 120, 104, 132, 241, 77, 25, 101, 169, 148, 58, 207, 127, 139, 115, 30, 254, 114, 79, 149, 13, 45, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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