Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3080a10a2f72adacc9ae70cdc7a8f7c6c776768334823642ee07e2f136b7cd5b

Tx prefix hash: a797359b85e050f7b931d271a6bfd94bb99d2dd5a4cda8f028bbfd5f2346c4f2
Tx public key: bb082b4f735f8b00f8e219a0f072b8ec1f9c2b65650fb9006b37c14135f55d2c
Timestamp: 1713622912 Timestamp [UCT]: 2024-04-20 14:21:52 Age [y:d:h:m:s]: 00:353:13:52:07
Block: 1004672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252778 RingCT/type: yes/0
Extra: 01bb082b4f735f8b00f8e219a0f072b8ec1f9c2b65650fb9006b37c14135f55d2c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b273eb56ef735eccf8ccc8e1968cf11afa1c32deeb873f3ac3b694e41a3bc117 0.600000000000 1465242 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": 1004682, "vin": [ { "gen": { "height": 1004672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b273eb56ef735eccf8ccc8e1968cf11afa1c32deeb873f3ac3b694e41a3bc117" } } ], "extra": [ 1, 187, 8, 43, 79, 115, 95, 139, 0, 248, 226, 25, 160, 240, 114, 184, 236, 31, 156, 43, 101, 101, 15, 185, 0, 107, 55, 193, 65, 53, 245, 93, 44, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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