Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb4f70096469f13afdba65fe9820701ff9d826364ee8db108b090533aab9da83

Tx prefix hash: 930754070b91d243fd725f2feb5bdeca37d7f781246bbe5746e392b442b808e0
Tx public key: e8d1f8f205df9c5299f9f2bb9144a4d208abe65b80a2ecda8adffb2f16bbb4a2
Timestamp: 1728909877 Timestamp [UCT]: 2024-10-14 12:44:37 Age [y:d:h:m:s]: 00:041:06:17:34
Block: 1131429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29448 RingCT/type: yes/0
Extra: 01e8d1f8f205df9c5299f9f2bb9144a4d208abe65b80a2ecda8adffb2f16bbb4a2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df96f8729ec770a3df7e707dd2fb46dd5fdd6472a9b092bc9f7d221a82ce230a 0.600000000000 1614328 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": 1131439, "vin": [ { "gen": { "height": 1131429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df96f8729ec770a3df7e707dd2fb46dd5fdd6472a9b092bc9f7d221a82ce230a" } } ], "extra": [ 1, 232, 209, 248, 242, 5, 223, 156, 82, 153, 249, 242, 187, 145, 68, 164, 210, 8, 171, 230, 91, 128, 162, 236, 218, 138, 223, 251, 47, 22, 187, 180, 162, 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