Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0741d0f31878e28f530c8972720d4b8c86da8f159a55fa11c89eb5ad806a69f5

Tx prefix hash: 51de0fbdab74ea130314446475e7ebcc78a2fc79018605f98cafd237d06f716d
Tx public key: aefcdd9291e50214aa116994d374a3b8cb4a679173ca47a0878b97a7b5ce35dd
Timestamp: 1717867680 Timestamp [UCT]: 2024-06-08 17:28:00 Age [y:d:h:m:s]: 00:228:10:38:43
Block: 1039877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163439 RingCT/type: yes/0
Extra: 01aefcdd9291e50214aa116994d374a3b8cb4a679173ca47a0878b97a7b5ce35dd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adb933c1805001b4210adfd5a6a954f5aa854db3f3005fb852b51ca8a7c8fa9a 0.600000000000 1508532 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": 1039887, "vin": [ { "gen": { "height": 1039877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adb933c1805001b4210adfd5a6a954f5aa854db3f3005fb852b51ca8a7c8fa9a" } } ], "extra": [ 1, 174, 252, 221, 146, 145, 229, 2, 20, 170, 17, 105, 148, 211, 116, 163, 184, 203, 74, 103, 145, 115, 202, 71, 160, 135, 139, 151, 167, 181, 206, 53, 221, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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