Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0483448d3420a4239c93af2e814c2f5881c6c3f0eb9957cd8927a6925ade31dd

Tx prefix hash: 021cd9e9640c4dc1ca4b05b2da370825798bded927c31945874240e961963d1d
Tx public key: 4a2626939e98260e92f2dbdbc60d159371f869018841fcc8f3892e726c63029e
Timestamp: 1719129709 Timestamp [UCT]: 2024-06-23 08:01:49 Age [y:d:h:m:s]: 00:326:20:46:19
Block: 1050324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233609 RingCT/type: yes/0
Extra: 014a2626939e98260e92f2dbdbc60d159371f869018841fcc8f3892e726c63029e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d2e87bbf5e17ab73c2ce9f0e9de1ddbfa52439a2c3b26ad4b06e1b3c0f718ad 0.600000000000 1520489 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": 1050334, "vin": [ { "gen": { "height": 1050324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d2e87bbf5e17ab73c2ce9f0e9de1ddbfa52439a2c3b26ad4b06e1b3c0f718ad" } } ], "extra": [ 1, 74, 38, 38, 147, 158, 152, 38, 14, 146, 242, 219, 219, 198, 13, 21, 147, 113, 248, 105, 1, 136, 65, 252, 200, 243, 137, 46, 114, 108, 99, 2, 158, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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