Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b863f263a8dacd842719d9111b8bdc5f3b7bfc6a4a1c4425b263af2596f21a3

Tx prefix hash: 38f113ab3bf3d1e780a4dfecd2778ceeb5f03f37341881fc914b1657b230bedb
Tx public key: e515905b26366b958cd82aeb9db3e90df1bee8603068de0e83c212231058c3cc
Timestamp: 1680629667 Timestamp [UCT]: 2023-04-04 17:34:27 Age [y:d:h:m:s]: 02:013:08:42:07
Block: 731909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531207 RingCT/type: yes/0
Extra: 01e515905b26366b958cd82aeb9db3e90df1bee8603068de0e83c212231058c3cc021100000002b3164c24000000000000000000

1 output(s) for total of 2.306119897000 dcy

stealth address amount amount idx
00: 65bdc70e066acbf0ad0c1d577d0ee60b679f1acb23aee510da628b2b454c71a4 2.306119897000 1177754 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": 731919, "vin": [ { "gen": { "height": 731909 } } ], "vout": [ { "amount": 2306119897, "target": { "key": "65bdc70e066acbf0ad0c1d577d0ee60b679f1acb23aee510da628b2b454c71a4" } } ], "extra": [ 1, 229, 21, 144, 91, 38, 54, 107, 149, 140, 216, 42, 235, 157, 179, 233, 13, 241, 190, 232, 96, 48, 104, 222, 14, 131, 194, 18, 35, 16, 88, 195, 204, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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