Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb47e86547bda44c3297482c736b0c4551c3f6a3cca403a0e0e0a52174e7f1c6

Tx prefix hash: 0f3e5ff354fd8768f438968d1db04267cc601d4cccb2406e38f3d6bbda62ad25
Tx public key: 37ca898610e9e7d4c3ad2a3b1a9e9478cdb051af598bd8e76930558f5646ecb2
Timestamp: 1738433907 Timestamp [UCT]: 2025-02-01 18:18:27 Age [y:d:h:m:s]: 00:292:13:26:07
Block: 1209955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206844 RingCT/type: yes/0
Extra: 0137ca898610e9e7d4c3ad2a3b1a9e9478cdb051af598bd8e76930558f5646ecb20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c6f71f1ead67ac63dd3b5f108ac4a89e54305c16d8d0a43d8dc31b119658d28 0.600000000000 1696702 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": 1209965, "vin": [ { "gen": { "height": 1209955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c6f71f1ead67ac63dd3b5f108ac4a89e54305c16d8d0a43d8dc31b119658d28" } } ], "extra": [ 1, 55, 202, 137, 134, 16, 233, 231, 212, 195, 173, 42, 59, 26, 158, 148, 120, 205, 176, 81, 175, 89, 139, 216, 231, 105, 48, 85, 143, 86, 70, 236, 178, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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