Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c188e60b8976078661be14d7f324f10f56330b9cd0e427494b41d851414b15

Tx prefix hash: aee810fff10d600f490bdc27dd267c1c6283622fadc4c2d309a134ba0c08f545
Tx public key: 51ce9f9bee7d6360c5126ba8a0c0295c3a3613d53bbe9fcb2a76b5a0cff0f1d8
Timestamp: 1581665940 Timestamp [UCT]: 2020-02-14 07:39:00 Age [y:d:h:m:s]: 05:022:01:06:34
Block: 64674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168603 RingCT/type: yes/0
Extra: 0151ce9f9bee7d6360c5126ba8a0c0295c3a3613d53bbe9fcb2a76b5a0cff0f1d802110000000112c4732d000000000000000000

1 output(s) for total of 374.728286644000 dcy

stealth address amount amount idx
00: 0f9f373aa08daa63ba06be0698af8c5beac895d6fa84cd3feaa796e4036fd9a4 374.728286644000 119324 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": 64684, "vin": [ { "gen": { "height": 64674 } } ], "vout": [ { "amount": 374728286644, "target": { "key": "0f9f373aa08daa63ba06be0698af8c5beac895d6fa84cd3feaa796e4036fd9a4" } } ], "extra": [ 1, 81, 206, 159, 155, 238, 125, 99, 96, 197, 18, 107, 168, 160, 192, 41, 92, 58, 54, 19, 213, 59, 190, 159, 203, 42, 118, 181, 160, 207, 240, 241, 216, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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