Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60eba542c5c9c6a395b9dbea54b816a64ff36f5cdf28914ecbd4e5b3593e893e

Tx prefix hash: 81227ab187395c374578f119dd1c462a2ad5e4c237533f9b3b5c8ef0b5169a26
Tx public key: 371a0cb32667eab8ac033dab7f544556dc84823e9c1c8404fabe7e4139a476f8
Timestamp: 1704303766 Timestamp [UCT]: 2024-01-03 17:42:46 Age [y:d:h:m:s]: 01:359:19:24:35
Block: 927423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516049 RingCT/type: yes/0
Extra: 01371a0cb32667eab8ac033dab7f544556dc84823e9c1c8404fabe7e4139a476f802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bea32fa1ad4e46aa5a740a7bd4bae7a93848384c1752b1b52568e950c269e05f 0.600000000000 1385259 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": 927433, "vin": [ { "gen": { "height": 927423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bea32fa1ad4e46aa5a740a7bd4bae7a93848384c1752b1b52568e950c269e05f" } } ], "extra": [ 1, 55, 26, 12, 179, 38, 103, 234, 184, 172, 3, 61, 171, 127, 84, 69, 86, 220, 132, 130, 62, 156, 28, 132, 4, 250, 190, 126, 65, 57, 164, 118, 248, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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