Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44cd163b0911ac9eae3a4948a5ee9d779492c1c7b80a242aa466e333da5a710c

Tx prefix hash: f1b412840cb68da1c7a2a402b752d4c3b6c176f2d29d4711ee191a5c00ff494e
Tx public key: 60f014e9e47be991b0cf3cffb8d6eb69afc3c743873baf59b8e5771a352282ca
Timestamp: 1751496586 Timestamp [UCT]: 2025-07-02 22:49:46 Age [y:d:h:m:s]: 00:134:11:55:55
Block: 1317529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94364 RingCT/type: yes/0
Extra: 0160f014e9e47be991b0cf3cffb8d6eb69afc3c743873baf59b8e5771a352282ca02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f76652c8b2306341cb431ea40fd904c7761b153f8be60f2b0c726c99d70446e 0.600000000000 1805198 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": 1317539, "vin": [ { "gen": { "height": 1317529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f76652c8b2306341cb431ea40fd904c7761b153f8be60f2b0c726c99d70446e" } } ], "extra": [ 1, 96, 240, 20, 233, 228, 123, 233, 145, 176, 207, 60, 255, 184, 214, 235, 105, 175, 195, 199, 67, 135, 59, 175, 89, 184, 229, 119, 26, 53, 34, 130, 202, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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