Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e1bbb68ce087775f3655f7fd89cb4be14456a9f3a9f2b8d00a64ffc4ab14fa

Tx prefix hash: 24478696688ba2fdb8850c59793aed2bea2a07356bf91868081cac55f61934db
Tx public key: 89c5bef416ea55bf1c86a73590f4b8cf0dd6783e43a7631c7c79e71f93429dcc
Timestamp: 1734031705 Timestamp [UCT]: 2024-12-12 19:28:25 Age [y:d:h:m:s]: 00:113:15:49:54
Block: 1173801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81001 RingCT/type: yes/0
Extra: 0189c5bef416ea55bf1c86a73590f4b8cf0dd6783e43a7631c7c79e71f93429dcc021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12f7f7900aadc45b7377384ee8a38e5b0a89ee4f08b92512ab86bc93eb67944e 0.600000000000 1659866 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": 1173811, "vin": [ { "gen": { "height": 1173801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12f7f7900aadc45b7377384ee8a38e5b0a89ee4f08b92512ab86bc93eb67944e" } } ], "extra": [ 1, 137, 197, 190, 244, 22, 234, 85, 191, 28, 134, 167, 53, 144, 244, 184, 207, 13, 214, 120, 62, 67, 167, 99, 28, 124, 121, 231, 31, 147, 66, 157, 204, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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