Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6596aeff56b533090e9ccb1088d197c37dea3ac343a1a6409168f7303fcb3fdb

Tx prefix hash: a859f4d31e858e259a842c08dd9ccee5a1865491699af4099b48b1e55c518812
Tx public key: a1b80d9addca90cc2279e9fbb0c4d112dc34dbbb090b37ff1a40307e40fed601
Timestamp: 1735082997 Timestamp [UCT]: 2024-12-24 23:29:57 Age [y:d:h:m:s]: 00:096:22:30:49
Block: 1182481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69068 RingCT/type: yes/0
Extra: 01a1b80d9addca90cc2279e9fbb0c4d112dc34dbbb090b37ff1a40307e40fed601021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82b44e4f706bfee211fe944651a48d78b3ae86bd87f30175d9f8e88d726bfed7 0.600000000000 1668916 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": 1182491, "vin": [ { "gen": { "height": 1182481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82b44e4f706bfee211fe944651a48d78b3ae86bd87f30175d9f8e88d726bfed7" } } ], "extra": [ 1, 161, 184, 13, 154, 221, 202, 144, 204, 34, 121, 233, 251, 176, 196, 209, 18, 220, 52, 219, 187, 9, 11, 55, 255, 26, 64, 48, 126, 64, 254, 214, 1, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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