Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4481b2880a3c85aab86c4c667dac52d56c3c1be789e1b0c338e3d29de23ea031

Tx prefix hash: 85256584421ce9fa2084736a1514b7ec11d557c7a73ff4550ca7bc21a33e3801
Tx public key: 000aa6fc9f15a097844ddd2f618b51360a654487ce76168d83d6b371a6fb26aa
Timestamp: 1677725421 Timestamp [UCT]: 2023-03-02 02:50:21 Age [y:d:h:m:s]: 02:027:18:46:37
Block: 707960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541424 RingCT/type: yes/0
Extra: 01000aa6fc9f15a097844ddd2f618b51360a654487ce76168d83d6b371a6fb26aa0211000000035029cbac000000000000000000

1 output(s) for total of 2.768436289000 dcy

stealth address amount amount idx
00: 7db0e67cc1c9a904c02a69b3150db0460eb41093fe27ab4c138f5a3a0d4a47d8 2.768436289000 1151791 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": 707970, "vin": [ { "gen": { "height": 707960 } } ], "vout": [ { "amount": 2768436289, "target": { "key": "7db0e67cc1c9a904c02a69b3150db0460eb41093fe27ab4c138f5a3a0d4a47d8" } } ], "extra": [ 1, 0, 10, 166, 252, 159, 21, 160, 151, 132, 77, 221, 47, 97, 139, 81, 54, 10, 101, 68, 135, 206, 118, 22, 141, 131, 214, 179, 113, 166, 251, 38, 170, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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