Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18511fda7165c5e33f1f04d0bafe9ab3ab17ac6018f2e57b92f300d4fd1424b7

Tx prefix hash: 6bdeb173f94846dd05f17ed57c3a958f240d85d82baa4c6f17afe2c686c67cd5
Tx public key: 45e6736d6c7ea672f833c834095d4136ca70601632dbc1f6c4fe43dc7620eb5e
Timestamp: 1698543404 Timestamp [UCT]: 2023-10-29 01:36:44 Age [y:d:h:m:s]: 01:232:23:02:19
Block: 879880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427421 RingCT/type: yes/0
Extra: 0145e6736d6c7ea672f833c834095d4136ca70601632dbc1f6c4fe43dc7620eb5e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.745748378000 dcy

stealth address amount amount idx
00: 4c4617dd66e07a625692e3a7fcf344fa988592fa7661038e660384851757a442 0.745748378000 1335420 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": 879890, "vin": [ { "gen": { "height": 879880 } } ], "vout": [ { "amount": 745748378, "target": { "key": "4c4617dd66e07a625692e3a7fcf344fa988592fa7661038e660384851757a442" } } ], "extra": [ 1, 69, 230, 115, 109, 108, 126, 166, 114, 248, 51, 200, 52, 9, 93, 65, 54, 202, 112, 96, 22, 50, 219, 193, 246, 196, 254, 67, 220, 118, 32, 235, 94, 2, 17, 0, 0, 0, 4, 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