Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f705052195a3f2019f99b5a86b6abea77d358c60b26c096fb01b90fdb95d33a

Tx prefix hash: bc7a19b947bc9a48c222ea34d7fc451a363de8d57910e92ce336f631486740c0
Tx public key: 306a88ec92dd750b5418bc3fe7ffda9f17bac26a3b178a87c68c050d22d95a7c
Timestamp: 1712710697 Timestamp [UCT]: 2024-04-10 00:58:17 Age [y:d:h:m:s]: 00:321:05:19:49
Block: 997103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229637 RingCT/type: yes/0
Extra: 01306a88ec92dd750b5418bc3fe7ffda9f17bac26a3b178a87c68c050d22d95a7c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d1f2f7df3752e00316f5ca21cba314c52dcefb6d3f222551192dc7cc27c9a89 0.600000000000 1457531 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": 997113, "vin": [ { "gen": { "height": 997103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1f2f7df3752e00316f5ca21cba314c52dcefb6d3f222551192dc7cc27c9a89" } } ], "extra": [ 1, 48, 106, 136, 236, 146, 221, 117, 11, 84, 24, 188, 63, 231, 255, 218, 159, 23, 186, 194, 106, 59, 23, 138, 135, 198, 140, 5, 13, 34, 217, 90, 124, 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