Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4bafebafdb4a6e4b5c91e5f8d4271a55a11496e608d13008f14e34bf47b3d16

Tx prefix hash: 057848ebb5a3997917aca2b9681d6e4823b0c6e5309eb3744899e1db1eca479d
Tx public key: 1d1a4f4ce9ee3c4d76c8d4b97ea3eb3925c298245fed4e825ea7d96acd44b4b4
Timestamp: 1727708076 Timestamp [UCT]: 2024-09-30 14:54:36 Age [y:d:h:m:s]: 00:195:00:53:46
Block: 1121467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139204 RingCT/type: yes/0
Extra: 011d1a4f4ce9ee3c4d76c8d4b97ea3eb3925c298245fed4e825ea7d96acd44b4b402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61ea6f84485e0cc732fd605c3bac4749b6516727df024e1ddccebd064daaa37c 0.600000000000 1603740 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": 1121477, "vin": [ { "gen": { "height": 1121467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61ea6f84485e0cc732fd605c3bac4749b6516727df024e1ddccebd064daaa37c" } } ], "extra": [ 1, 29, 26, 79, 76, 233, 238, 60, 77, 118, 200, 212, 185, 126, 163, 235, 57, 37, 194, 152, 36, 95, 237, 78, 130, 94, 167, 217, 106, 205, 68, 180, 180, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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