Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7189e9da3db961dd62348c8078d708d65ddbe5661b0753d272e2f1116559a87a

Tx prefix hash: a682d3fc6238d47dce64c0c197ce0cece01cbe63698f9308ec0476ccfe27737c
Tx public key: a33e9e7fb8f076b386bdcd501d761d4a54aee2a033ff96ca949ecda085006aee
Timestamp: 1726367593 Timestamp [UCT]: 2024-09-15 02:33:13 Age [y:d:h:m:s]: 00:061:00:39:14
Block: 1110344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43617 RingCT/type: yes/0
Extra: 01a33e9e7fb8f076b386bdcd501d761d4a54aee2a033ff96ca949ecda085006aee021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8683e249a7cf6b5fc5d19079fac1a2f7d2388b6d3612daee0c46448b8e689be3 0.600000000000 1588913 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": 1110354, "vin": [ { "gen": { "height": 1110344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8683e249a7cf6b5fc5d19079fac1a2f7d2388b6d3612daee0c46448b8e689be3" } } ], "extra": [ 1, 163, 62, 158, 127, 184, 240, 118, 179, 134, 189, 205, 80, 29, 118, 29, 74, 84, 174, 226, 160, 51, 255, 150, 202, 148, 158, 205, 160, 133, 0, 106, 238, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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