Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248834da1d9c4c31e1b37c43f4cba67504829bfa2f900a50b2942f7608cb4083

Tx prefix hash: b00c120a036c729fbf249b156c167e90321f837f98513d97a615f567c6f7b81d
Tx public key: f4dc9fe2345f8ee15f4d60de755369789a732e17192c4e98f6466c0d563d5156
Timestamp: 1677715584 Timestamp [UCT]: 2023-03-02 00:06:24 Age [y:d:h:m:s]: 02:249:14:15:11
Block: 707879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697666 RingCT/type: yes/0
Extra: 01f4dc9fe2345f8ee15f4d60de755369789a732e17192c4e98f6466c0d563d51560211000000025029cbac000000000000000000

1 output(s) for total of 2.770147666000 dcy

stealth address amount amount idx
00: 3852d159b9e5d2caee0ce499733f2b72560ec9b6008c38fa0c78407dbabc952a 2.770147666000 1151708 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": 707889, "vin": [ { "gen": { "height": 707879 } } ], "vout": [ { "amount": 2770147666, "target": { "key": "3852d159b9e5d2caee0ce499733f2b72560ec9b6008c38fa0c78407dbabc952a" } } ], "extra": [ 1, 244, 220, 159, 226, 52, 95, 142, 225, 95, 77, 96, 222, 117, 83, 105, 120, 154, 115, 46, 23, 25, 44, 78, 152, 246, 70, 108, 13, 86, 61, 81, 86, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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