Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245e1e450fbbdae0ef9f95882a3dbc19cd1e7ba13dd728fefd748e2a765f1968

Tx prefix hash: 84ce4b4bbd3dd8dce121850ad662f3c644829fd8bc003a2a0a3b76fecedf2a27
Tx public key: f1e62886e29d094f2b9492442653ecda02e10f823a0a1ffd3f19afdf664f169d
Timestamp: 1676458994 Timestamp [UCT]: 2023-02-15 11:03:14 Age [y:d:h:m:s]: 02:083:03:35:49
Block: 697464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581048 RingCT/type: yes/0
Extra: 01f1e62886e29d094f2b9492442653ecda02e10f823a0a1ffd3f19afdf664f169d02110000000374b6d784000000000000000000

1 output(s) for total of 2.999246453000 dcy

stealth address amount amount idx
00: 29aa68bf5a738174a460d52bb28fc420e5a0c3d8888e37afcf34ee7b3b7c1046 2.999246453000 1140651 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": 697474, "vin": [ { "gen": { "height": 697464 } } ], "vout": [ { "amount": 2999246453, "target": { "key": "29aa68bf5a738174a460d52bb28fc420e5a0c3d8888e37afcf34ee7b3b7c1046" } } ], "extra": [ 1, 241, 230, 40, 134, 226, 157, 9, 79, 43, 148, 146, 68, 38, 83, 236, 218, 2, 225, 15, 130, 58, 10, 31, 253, 63, 25, 175, 223, 102, 79, 22, 157, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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