Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0fc70df2f6dce013ccb0785a0960c447796a320eadd8eb7b7ecdccd420d2d1

Tx prefix hash: 4e2823ed1d1483919dafdcaeff9ed58db45a3181361a156a38dc1991349ad8a8
Tx public key: fd4d4e59559ff814166c0d004edcff5a8ee2762e39c916f15d4c7e00342ce791
Timestamp: 1677027151 Timestamp [UCT]: 2023-02-22 00:52:31 Age [y:d:h:m:s]: 02:258:20:12:30
Block: 702169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704293 RingCT/type: yes/0
Extra: 01fd4d4e59559ff814166c0d004edcff5a8ee2762e39c916f15d4c7e00342ce79102110000000174b6d784000000000000000000

1 output(s) for total of 2.893493619000 dcy

stealth address amount amount idx
00: 1820e3fb60e0fa7e28e616d89e03c7beecaa686351943cd4c6b6afbf9823af60 2.893493619000 1145668 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": 702179, "vin": [ { "gen": { "height": 702169 } } ], "vout": [ { "amount": 2893493619, "target": { "key": "1820e3fb60e0fa7e28e616d89e03c7beecaa686351943cd4c6b6afbf9823af60" } } ], "extra": [ 1, 253, 77, 78, 89, 85, 159, 248, 20, 22, 108, 13, 0, 78, 220, 255, 90, 142, 226, 118, 46, 57, 201, 22, 241, 93, 76, 126, 0, 52, 44, 231, 145, 2, 17, 0, 0, 0, 1, 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