Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a632b75a105035664c2648834fc81f8c0d816f57d2672f9c1313160ce9a0b0b

Tx prefix hash: 36ad283394c0bd1d15a4513042ba7f0b81a0bae4a7acc0182d452697e4705704
Tx public key: 8b8c6264e312bea4ed238e9a926e25b195850f7ff28feac1fc9beadb43c429d3
Timestamp: 1706907288 Timestamp [UCT]: 2024-02-02 20:54:48 Age [y:d:h:m:s]: 01:135:20:43:51
Block: 948994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358111 RingCT/type: yes/0
Extra: 018b8c6264e312bea4ed238e9a926e25b195850f7ff28feac1fc9beadb43c429d30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb60ae575de6c515d015ed9f8ddbe71302c5411efb374a38ce2331d32e165026 0.600000000000 1407516 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": 949004, "vin": [ { "gen": { "height": 948994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb60ae575de6c515d015ed9f8ddbe71302c5411efb374a38ce2331d32e165026" } } ], "extra": [ 1, 139, 140, 98, 100, 227, 18, 190, 164, 237, 35, 142, 154, 146, 110, 37, 177, 149, 133, 15, 127, 242, 143, 234, 193, 252, 155, 234, 219, 67, 196, 41, 211, 2, 17, 0, 0, 0, 2, 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