Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ace5337c8a7dac5351de082368a92a4431f9a8c850711ba8a44ee7193c3fcd

Tx prefix hash: e45fee359a140d8a68f5781185f4858d19641985470241dbd6b951d4b18a3549
Tx public key: 89c914f0d7bf22ba0d48563710d9a4cd3d82ecf7056c42a6d32cd3831deaa501
Timestamp: 1717332822 Timestamp [UCT]: 2024-06-02 12:53:42 Age [y:d:h:m:s]: 00:347:12:34:48
Block: 1035459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248369 RingCT/type: yes/0
Extra: 0189c914f0d7bf22ba0d48563710d9a4cd3d82ecf7056c42a6d32cd3831deaa5010211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a24ff177ec419f8127a17c1582a1800dc51ac2cb868c1ca2941fef3b2a4e4a 0.600000000000 1503980 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": 1035469, "vin": [ { "gen": { "height": 1035459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a24ff177ec419f8127a17c1582a1800dc51ac2cb868c1ca2941fef3b2a4e4a" } } ], "extra": [ 1, 137, 201, 20, 240, 215, 191, 34, 186, 13, 72, 86, 55, 16, 217, 164, 205, 61, 130, 236, 247, 5, 108, 66, 166, 211, 44, 211, 131, 29, 234, 165, 1, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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