Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b585dfbf9f08d7b86de8183e8f4a6f0cbe6602f804779a9b5f82032e1860e15d

Tx prefix hash: ea674ab5b4fb829d50f721400a7262fbda2ff7934976d9e91196214994d7cb84
Tx public key: beaef0c438408e32b95c601b1f65a15de622c23b83452f6bff967ba6e4420a68
Timestamp: 1713868556 Timestamp [UCT]: 2024-04-23 10:35:56 Age [y:d:h:m:s]: 01:194:02:19:54
Block: 1006724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397347 RingCT/type: yes/0
Extra: 01beaef0c438408e32b95c601b1f65a15de622c23b83452f6bff967ba6e4420a6802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6cd98f3a8adf4fb3483075fafb449e7c68931d8550c3be92c30329b918f1d8 0.600000000000 1467842 of 15

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": 1006734, "vin": [ { "gen": { "height": 1006724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6cd98f3a8adf4fb3483075fafb449e7c68931d8550c3be92c30329b918f1d8" } } ], "extra": [ 1, 190, 174, 240, 196, 56, 64, 142, 50, 185, 92, 96, 27, 31, 101, 161, 93, 230, 34, 194, 59, 131, 69, 47, 107, 255, 150, 123, 166, 228, 66, 10, 104, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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