Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611c19fa56d5e02aaa5074c8451295cb79c421ce866c634e050f230399cea75a

Tx prefix hash: be3df7bedf8e61d4cf83fad952cf806f1ea42177ddb8d8cff5ea99a3e0a44762
Tx public key: b1891e3c1abf5a6c3755c845331c2cc1daeb9821d3367f395f849b3f03ed91f5
Timestamp: 1705755437 Timestamp [UCT]: 2024-01-20 12:57:17 Age [y:d:h:m:s]: 01:080:22:55:29
Block: 939427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318969 RingCT/type: yes/0
Extra: 01b1891e3c1abf5a6c3755c845331c2cc1daeb9821d3367f395f849b3f03ed91f50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b3e332536802814414384e84ee5f7d6af9d49ca083ef02ba9ad98346a7f0cfe 0.600000000000 1397535 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": 939437, "vin": [ { "gen": { "height": 939427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b3e332536802814414384e84ee5f7d6af9d49ca083ef02ba9ad98346a7f0cfe" } } ], "extra": [ 1, 177, 137, 30, 60, 26, 191, 90, 108, 55, 85, 200, 69, 51, 28, 44, 193, 218, 235, 152, 33, 211, 54, 127, 57, 95, 132, 155, 63, 3, 237, 145, 245, 2, 17, 0, 0, 0, 3, 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