Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0706345adcfd6a61de004ad8412625bc186c1c6144d830ba7aa1df10f9e476d8

Tx prefix hash: 283318e131427d62a120e290c24de0175bff377470d09fb28f28087a599a976f
Tx public key: 44acd2847d817dd8e3c332ced9080c8bb18c6fe17a4a075d1fc3515ceada0564
Timestamp: 1700790326 Timestamp [UCT]: 2023-11-24 01:45:26 Age [y:d:h:m:s]: 01:093:12:27:10
Block: 898290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327976 RingCT/type: yes/0
Extra: 0144acd2847d817dd8e3c332ced9080c8bb18c6fe17a4a075d1fc3515ceada056402110000000333af99f4000000000000000000

1 output(s) for total of 0.648025831000 dcy

stealth address amount amount idx
00: 1ea9eff6774b87ce4e4a8159042da3a9e524c3abc9bc527fa5af99f0c2284dcb 0.648025831000 1354703 of 0

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": 898300, "vin": [ { "gen": { "height": 898290 } } ], "vout": [ { "amount": 648025831, "target": { "key": "1ea9eff6774b87ce4e4a8159042da3a9e524c3abc9bc527fa5af99f0c2284dcb" } } ], "extra": [ 1, 68, 172, 210, 132, 125, 129, 125, 216, 227, 195, 50, 206, 217, 8, 12, 139, 177, 140, 111, 225, 122, 74, 7, 93, 31, 195, 81, 92, 234, 218, 5, 100, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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