Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487b09b73def41085fc1b800340700fdec3481454e33788d50ff1503b4578910

Tx prefix hash: 9e200328e015e6db22ac5421d9f3a2845e62f5f401d29fb16d94a8c0e8ef5742
Tx public key: abfb7524e49d5a3139b402d2154bc8a7d09a9d70858a0febcf9d590fd8bf75b0
Timestamp: 1699841521 Timestamp [UCT]: 2023-11-13 02:12:01 Age [y:d:h:m:s]: 01:103:16:50:40
Block: 890446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335246 RingCT/type: yes/0
Extra: 01abfb7524e49d5a3139b402d2154bc8a7d09a9d70858a0febcf9d590fd8bf75b0021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.687991001000 dcy

stealth address amount amount idx
00: 3c4abd6bc8f6a3a2fec58a80f21270f991bb8b14abac8e593f7a5547811df272 0.687991001000 1346469 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": 890456, "vin": [ { "gen": { "height": 890446 } } ], "vout": [ { "amount": 687991001, "target": { "key": "3c4abd6bc8f6a3a2fec58a80f21270f991bb8b14abac8e593f7a5547811df272" } } ], "extra": [ 1, 171, 251, 117, 36, 228, 157, 90, 49, 57, 180, 2, 210, 21, 75, 200, 167, 208, 154, 157, 112, 133, 138, 15, 235, 207, 157, 89, 15, 216, 191, 117, 176, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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