Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db848e20de20d6106748d3c256bea0667667f892d5d6c3fd4831371f3eff958a

Tx prefix hash: 9895211eddda96c7942fcb9b600f6cd408a6c5f0c27fdd6bd651558db9222e16
Tx public key: 87e885674cd40ecdd736df0e1be2249ac36a21cf7e43bef6305a36c6a52f0cfd
Timestamp: 1581962610 Timestamp [UCT]: 2020-02-17 18:03:30 Age [y:d:h:m:s]: 05:060:04:10:18
Block: 66991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196007 RingCT/type: yes/0
Extra: 0187e885674cd40ecdd736df0e1be2249ac36a21cf7e43bef6305a36c6a52f0cfd0211000000044ac5aa02000000000000000000

1 output(s) for total of 368.168653240000 dcy

stealth address amount amount idx
00: 3072583a31e76357b2896132a0ce4c84c058bf70a8e1f4d054794e412eae07f5 368.168653240000 123350 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": 67001, "vin": [ { "gen": { "height": 66991 } } ], "vout": [ { "amount": 368168653240, "target": { "key": "3072583a31e76357b2896132a0ce4c84c058bf70a8e1f4d054794e412eae07f5" } } ], "extra": [ 1, 135, 232, 133, 103, 76, 212, 14, 205, 215, 54, 223, 14, 27, 226, 36, 154, 195, 106, 33, 207, 126, 67, 190, 246, 48, 90, 54, 198, 165, 47, 12, 253, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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