Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c538bd57376f73eb7d58214259bf70b2efab34bfda9ce913f649bc518b0bb6

Tx prefix hash: ee77b92a01d5af2e39ce473d9c89cb9d3df69dbdd1ea698b2692a3e56ebaa432
Tx public key: 96b643334334e2cbf86141aea4409cea29abef900aac58a8230fd7259e5f4e6f
Timestamp: 1719467433 Timestamp [UCT]: 2024-06-27 05:50:33 Age [y:d:h:m:s]: 01:157:17:21:38
Block: 1053130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371305 RingCT/type: yes/0
Extra: 0196b643334334e2cbf86141aea4409cea29abef900aac58a8230fd7259e5f4e6f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7e5d6ca411555df9b83768d444de6976353c9dddf79c4c69ab1b7e14071c70 0.600000000000 1523477 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": 1053140, "vin": [ { "gen": { "height": 1053130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7e5d6ca411555df9b83768d444de6976353c9dddf79c4c69ab1b7e14071c70" } } ], "extra": [ 1, 150, 182, 67, 51, 67, 52, 226, 203, 248, 97, 65, 174, 164, 64, 156, 234, 41, 171, 239, 144, 10, 172, 88, 168, 35, 15, 215, 37, 158, 95, 78, 111, 2, 17, 0, 0, 0, 4, 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