Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 629a1aec1e3bb3947b39ef957a32befc1774cbfe69f62fef494807eb79c72824

Tx prefix hash: 04af03263631423ef12a98f9bb4ea0d404cde8f48b5f0a7bd437ad8669c17272
Tx public key: b40c426d4c8d9a8fe3c5a0f75ecfa728740307dff59cbb489b79d5adf1d49bd2
Timestamp: 1703476721 Timestamp [UCT]: 2023-12-25 03:58:41 Age [y:d:h:m:s]: 01:149:08:27:08
Block: 920578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367886 RingCT/type: yes/0
Extra: 01b40c426d4c8d9a8fe3c5a0f75ecfa728740307dff59cbb489b79d5adf1d49bd2021100000009ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d194cf1796dce580a0182e8624739d5925bb6b8b2a4290fe70173f154a431f87 0.600000000000 1378258 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": 920588, "vin": [ { "gen": { "height": 920578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d194cf1796dce580a0182e8624739d5925bb6b8b2a4290fe70173f154a431f87" } } ], "extra": [ 1, 180, 12, 66, 109, 76, 141, 154, 143, 227, 197, 160, 247, 94, 207, 167, 40, 116, 3, 7, 223, 245, 156, 187, 72, 155, 121, 213, 173, 241, 212, 155, 210, 2, 17, 0, 0, 0, 9, 173, 86, 148, 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